ledger: 2026-05-15 cutover validation session (canon + smoke + follow-up)#213
Merged
Merged
Conversation
…ation DOLCHEO session record covering the 2026-05-14 telemetry-coverage handoff continuation through canon authoring (PRs #210, #211), smoke verification of the wrapper across main preview and prod (worker_version 0.28.0), and the diagnostic that opened PR #212 on the residual writeDataPoint flush race. Three primary outcomes: D1. Soak-and-statistical gate replaced with smoke-and-verify gate D3. Promotion shipped on smoke evidence; emit-loss filed as follow-up L1. Performed prudence can leak into canon authoring; canon-first is a check on session drift but cannot save canon written hastily
Canon Quality — Frontmatter Schema ✅All 41 file(s) in Validator: |
Canon Quality —
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
DOLCHEO session record for the cutover validation continuation.
What this captures
klappy://odd/handoffs/2026-05-14-telemetry-coverage-completenessframed validation as a 24-hour soak with statistical thresholds. That framing was performed prudence for oddkit's load profile.klappy://canon/constraints/telemetry-validation-gate(PR canon: add telemetry-validation-gate constraint #210 merged, PR fix(canon): correct SSE bytes_out claim in telemetry-validation-gate #211 fix-forward merged).klappy://canon/observations/2026-05-16-telemetry-wrapper-intermittent-emit-loss, and accepted as a follow-up fix (PR obs: telemetry wrapper intermittent writeDataPoint drops (follow-up to #157) #212, fix not yet implemented).Why this matters as a ledger entry
L1: performed prudence can leak into canon authoring. The very canon I wrote to govern the gate carried the 24-hour soak DNA until Klappy's correction. That's worth preserving as a lesson, not just a transient session detail.
Note
Low Risk
Low risk: this PR only adds a new ledger markdown document and does not modify runtime code, configs, or validation logic.
Overview
Adds a new session ledger entry
odd/ledger/2026-05-15-cutover-validation-session.mddocumenting the cutover validation outcome, including the shift from a 24-hour soak/threshold model to a deterministic smoke-and-verify gate, smoke evidence notes (byte-exactbytes_in, non-zero SSEbytes_out), and follow-up handoffs for intermittent telemetry emit-loss andcleanup_storageprivatization.Reviewed by Cursor Bugbot for commit e204ac3. Bugbot is set up for automated code reviews on this repo. Configure here.